Remote viewing of multimedia content

ABSTRACT

A method and system for remote viewing of multimedia content using a multimedia content distribution network (MCDN) is configured to duplicate multimedia content displayed on a first MCDN terminal device and route the duplicate multimedia content to a second MCDN terminal device. The MCDN terminal devices may be coupled to a local network at an MCDN client premises. The MCDN terminal devices may also include wireless telephony devices for mobile remote viewing functionality. The method may include transcoding of the multimedia content into a format suitable for the second MCDN terminal device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/160,156 filed May 20, 2016, which is a continuation of U.S. patentapplication Ser. No. 14/048,619 filed Oct. 8, 2013 (now U.S. Pat. No.9,374,627), which is a continuation of U.S. patent application Ser. No.12/574,439 filed Oct. 6, 2009 (now U.S. Pat. No. 8,555,406). Thecontents of each of the foregoing is/are hereby incorporated byreference into this application as if set forth herein in full.

FIELD OF THE DISCLOSURE

The present disclosure relates to remote viewing of multimedia contentand, more particularly, to remote viewing using a multimedia contentdistribution network (MCDN).

DESCRIPTION OF THE RELATED ART

Various terminal devices, including wireless and mobile devices, may becoupled to MCDN customer premises equipment (CPE) to receive and viewmultimedia content over an MCDN. The ability to transfer multimediacontent between MCDN terminal devices may entail cumbersome integrationof external equipment and may only provide restrictive remote viewingcapability.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of selected elements of an embodiment of amultimedia distribution network;

FIG. 2 is a block diagram of selected elements of an embodiment of amultimedia distribution network;

FIG. 3 is a block diagram of selected elements of an embodiment of amultimedia handling device;

FIG. 4 is a block diagram of selected elements of an embodiment of amultimedia distribution network device;

FIG. 5 is a block diagram of selected elements of an embodiment of amultimedia distribution network;

FIG. 6 is a flow chart illustrating selected elements of an embodimentof a method for remove viewing;

FIG. 7 is a flow chart illustrating selected elements of an embodimentof a method for remote viewing;

FIG. 8 is a user interface illustrating selected elements of anembodiment of a method for remote viewing; and

FIG. 9 is a user interface illustrating selected elements of anembodiment of a method for remote viewing.

DETAILED DESCRIPTION OF THE DRAWINGS

In one aspect, a disclosed method for a user to remotely view multimediacontent received over an MCDN includes transmitting first multimediacontent from an MCDN service provider to a first MCDN terminal deviceconfigured to display the first multimedia content. In response to auser request for remote viewing of the first MCDN terminal devicedisplay, the method may further include duplicating the first multimediacontent displayed on the first MCDN terminal device, the duplicatemultimedia content including the first multimedia content, fortransmission to a second MCDN terminal device. The method operation ofduplicating may further include transcoding the duplicate multimediacontent into a format suitable for the second MCDN terminal device. Themethod operation of duplicating may still further include obtainingdigital-rights management (DRM) authorization to perform saidduplicating.

In some instances, the method further includes transmitting theduplicate multimedia content to the second MCDN terminal device. Theduplicate multimedia content may be transmitted to a terminal serviceexecuting on the second MCDN terminal device. The first MCDN terminaldevice and the second MCDN terminal device may be selected from thefollowing device types: a television, a personal computer, a gamingconsole, and a mobile multimedia device. The first MCDN terminal deviceand the second MCDN terminal may be of different device types or of thesame device type. The mobile multimedia device may be configured forwireless telephony communication, while the method operation ofduplicating may further include transmitting the duplicate multimediacontent to a mobile content management server that is coupled to awireless transmission network providing wireless network service to themobile multimedia device.

In a further aspect, a disclosed CPE for use within a clientconfiguration of an MCDN includes a processor, a network adapter, andmemory media accessible to the processor, including instructionsexecutable by the processor. The processor instructions may beexecutable to receive first multimedia content from an MCDN server viathe network adapter, and send the first multimedia content to a firstMCDN terminal device coupled to the CPE and configured to display thefirst multimedia content. The processor instructions may further beexecutable to duplicate the first multimedia content displayed on thefirst MCDN terminal device, the duplicate multimedia content includingthe first multimedia content, and send the duplicate multimedia contentto a second MCDN terminal device coupled to the CPE. The first MCDNterminal device and the second MCDN terminal device may be coupled tothe CPE via a fixed network.

In some embodiments, the CPE further includes a local wireless networkadapter configured to provide wireless access to at least one of thefirst MCDN terminal device and the second MCDN terminal device. At leastone of the first MCDN terminal device and the second MCDN terminaldevice may be a mobile wireless telephony device configured to displaymultimedia content.

In certain instances, the processor executable instructions to send theduplicate multimedia content may further comprise processor executableinstructions to send the duplicate multimedia content to a mobilecontent management server coupled to a wireless transmission networkproviding wireless network service to the mobile wireless telephonydevice.

In yet another aspect, disclosed computer-readable memory media includeexecutable instructions for remote viewing of multimedia content over anMCDN. The instructions may be executable to receive first multimediacontent from an MCDN server, and send the first multimedia content to afirst MCDN terminal device configured to display the first multimediacontent. The instructions may further be executable to duplicate thefirst multimedia content, and send the duplicate multimedia content to asecond MCDN terminal device.

In certain implementations, the memory media may further includeinstructions executable to transcode the duplicate multimedia contentinto a format suitable for the second MCDN terminal device, wherein thefirst MCDN terminal device and the second MCDN terminal device aredifferent types of devices. The memory media may still further includeinstructions executable to obtain DRM authorization to duplicate thefirst multimedia content. The memory media may also include instructionsexecutable to send the duplicate multimedia content to a terminalservice executing on the second MCDN terminal device. The memory mediamay further include instructions executable to receive user input forselecting a terminal service on the first MCDN terminal device or thesecond MCDN terminal device. The memory media may yet further includeinstructions executable to receive user input for displaying anindication of transcoding between the first MCDN terminal device and thesecond MCDN terminal device. The memory media may also further includeinstructions executable to receive user input for displaying anindication of DRM for the duplicate multimedia content.

In the following description, details are set forth by way of example tofacilitate discussion of the disclosed subject matter. It should beapparent to a person of ordinary skill in the field, however, that thedisclosed embodiments are exemplary and not exhaustive of all possibleembodiments.

Throughout this disclosure, a hyphenated form of a reference numeralrefers to a specific instance of an element and the un-hyphenated formof the reference numeral refers to the element generically orcollectively. Thus, for example, widget 12-1 refers to an instance of awidget class, which may be referred to collectively as widgets 12 andany one of which may be referred to generically as a widget 12.

Turning now to the drawings, FIG. 1 is a block diagram illustratingselected elements of an embodiment of MCDN 100. Although multimediacontent is not limited to TV, video on demand (VOD), or pay-per-view(PPV) programs, the depicted embodiments of MCDN 100 and itscapabilities are primarily described herein with reference to thesetypes of multimedia content, which are interchangeably referred toherein as “multimedia content”, “multimedia content programs”,“multimedia programs” or, simply, “programs.”

The elements of MCDN 100 illustrated in FIG. 1 depict networkembodiments with functionality for delivering multimedia content to aset of one or more subscribers. It is noted that different embodimentsof MCDN 100 may include additional elements or systems (not shown inFIG. 1 for clarity) as desired for additional functionality, such asdata processing systems for billing, content management, customersupport, operational support, or other business applications.

As depicted in FIG. 1, MCDN 100 includes one or more clients 120 and aservice provider 121. Each client 120 may represent a differentsubscriber of MCDN 100. In FIG. 1, a plurality of n clients 120 isdepicted as client 120-1, client 120-2 to client 120-n, where n may be alarge number. Service provider 121 as depicted in FIG. 1 encompassesresources to acquire, process, and deliver programs to clients 120 viaaccess network 130. Such elements in FIG. 1 of service provider 121include content acquisition resources 180 connected to switching network140 via backbone network 170, as well as application server 150,database server 190, mobile content management server 162, and contentdelivery server 160, also shown connected to switching network 140.

Access network 130 demarcates clients 120 and service provider 121, andprovides at least one connection path between clients 120 and serviceprovider 121. In some embodiments, access network 130 is an Internetprotocol (IP) compliant network. In some embodiments, access network 130is, at least in part, a coaxial cable network. It is noted that in someembodiments of MCDN 100, access network 130 is owned and/or operated byservice provider 121. In other embodiments, a third party may own and/oroperate at least a portion of access network 130.

In IP-compliant embodiments of access network 130, access network 130may include a physical layer of unshielded twisted pair cables, fiberoptic cables, or a combination thereof. MCDN 100 may include digitalsubscribe line (DSL) compliant twisted pair connections between clients120 and a node (not depicted) in access network 130 while fiber, cableor another broadband medium connects service provider resources to thenode. In other embodiments, the broadband cable may extend all the wayto clients 120.

As depicted in FIG. 1, switching network 140 provides connectivity forservice provider 121, and may be housed in a central office or otherfacility of service provider 121. Switching network 140 may providefirewall and routing functions to demarcate access network 130 from theresources of service provider 121. In embodiments that employ DSLcompliant connections, switching network 140 may include elements of aDSL Access Multiplexer (DSLAM) that multiplexes many subscriber DSLs tobackbone network 170.

In FIG. 1, backbone network 170 represents a private network including,as an example, a fiber based network to accommodate high data transferrates. Content acquisition resources 180 as depicted in FIG. 1 encompassthe acquisition of various types of content including broadcast content,other “live” content including national content feeds, and VOD content.

Thus, the content provided by service provider 121 encompassesmultimedia content that is scheduled in advance for viewing by clients120 via access network 130. Such multimedia content, also referred toherein as “scheduled programming,” may be selected using an electronicprogramming guide (EPG), such as EPG 316 described below with respect toFIG. 3. Accordingly, a user of MCDN 100 may be able to browse scheduledprogramming well in advance of the broadcast date and time. Somescheduled programs may be “regularly” scheduled programs, which recur atregular intervals or at the same periodic date and time (i.e., daily,weekly, monthly, etc.). Programs which are broadcast at short notice orinterrupt scheduled programs are referred to herein as “unscheduledprogramming.”

Acquired content is provided to content delivery server 160 via backbonenetwork 170 and switching network 140. Content may be delivered fromcontent delivery server 160 to clients 120 via switching network 140 andaccess network 130. Content may be compressed, encrypted, modulated,demodulated, and otherwise encoded or processed at content acquisitionresources 180, content delivery server 160, or both. Although FIG. 1depicts a single element encompassing acquisition of all content,different types of content may be acquired via different types ofacquisition resources. Similarly, although FIG. 1 depicts a singlecontent delivery server 160, different types of content may be deliveredby different servers. Moreover, embodiments of MCDN 100 may includecontent acquisition resources in regional offices that are connected toswitching network 140.

Although service provider 121 is depicted in FIG. 1 as having switchingnetwork 140 to which content acquisition resources 180, content deliveryserver 160, and application server 150 are connected, other embodimentsmay employ different switching networks for each of these functionalcomponents and may include additional functional components (notdepicted in FIG. 1) including, for example, operational subsystemsupport (OSS) resources.

FIG. 1 also illustrates application server 150 connected to switchingnetwork 140. As suggested by its name, application server 150 may hostor otherwise implement one or more applications for MCDN 100.Application server 150 may be any data processing system with associatedsoftware that provides applications for clients or users. Applicationserver 150 may provide services including multimedia content services,e.g., EPGs, digital video recording (DVR) services, VOD programs, PPVprograms, IPTV portals, digital rights management (DRM) servers,navigation/middleware servers, conditional access systems (CAS), andremote diagnostics, as examples.

Applications provided by application server 150 may be downloaded andhosted on other network resources including, for example, contentdelivery server 160, switching network 140, and/or on clients 120.Application server 150 is configured with a processor and storage media(not shown in FIG. 1) and is enabled to execute processor instructions,such as those included within a software application. As depicted inFIG. 1, application server 150 may be configured to include remoteviewer application 152, which, as will be described in detail below, maybe configured to enable a user of client 120 of MCDN 100 to remotelyview multimedia content.

Further depicted in FIG. 1 is database server 190, which provideshardware and software resources for data warehousing. Database server190 may communicate with other elements of the resources of serviceprovider 121, such as application server 150 or content delivery server160, in order to store and provide access to large volumes of data,information, or multimedia content. In some embodiments, database server190 includes a data warehousing application, accessible via switchingnetwork 140, that can be used to record and access structured data, suchas program or channel metadata for clients 120. Database server 190 mayalso store device information, such as identifiers for client 120, andidentifiers for various types of MCDN terminal devices.

Turning now to FIG. 2, clients 120 are shown in additional detail withrespect to access network 130. Clients 120 may include a networkappliances collectively referred to herein as CPE 122. In the depictedembodiment, CPE 122 includes the following devices: gateway (GW) 123,multimedia handling device (MHD) 125, and display device 126. Anycombination of GW 123, MHD 125, and display device 126 may be integratedinto a single physical device. Thus, for example, CPE 122 might includea single physical device that integrates GW 123, MHD 125, and displaydevice 126. As another example, MHD 125 may be integrated into displaydevice 126, while GW 123 is housed within a physically separate device.

In FIG. 2, GW 123 provides connectivity for client 120 to access network130. GW 123 provides an interface and conversion function between accessnetwork 130 and client-side local area network (LAN) 124. GW 123 mayinclude elements of a conventional DSL or cable modem. GW 123, in someembodiments, may further include routing functionality for routingmultimedia content, conventional data content, or a combination of bothin compliance with IP or another network layer protocol. In someembodiments, LAN 124 may encompass or represent an IEEE 802.3 (Ethernet)LAN, an IEEE 802.11-type (WiFi) LAN, or a combination thereof. GW 123may still further include WiFi or another type of wireless access pointto extend LAN 124 to wireless-capable devices in proximity to GW 123. GW123 may also provide a firewall (not depicted) between clients 120 andaccess network 130.

Clients 120 as depicted in FIG. 2 further include a display device or,more simply, a display 126. Display 126 may be implemented as a TV, aliquid crystal display screen, a computer monitor, or the like. Display126 may comply with a display standard such as National TelevisionSystem Committee (NTSC), Phase Alternating Line (PAL), or anothersuitable standard. Display 126 may include one or more integratedspeakers to play audio content.

Clients 120 are further shown with their respective remote control (RC)128, which is configured to control the operation of MHD 125 by means ofa user interface (not shown in FIG. 2) displayed on display 126. RC 128of client 120 is operable to communicate requests or commands wirelesslyto MHD 125 using infrared (IR) or radio frequency (RF) signals. MHDs 125may also receive requests or commands via buttons (not depicted) locatedon side panels of MHDs 125. In some embodiments, RC 128 may be operableto configure remote viewing of multimedia content, and/or to activateremote viewing of multimedia content, as will be described in detailbelow.

MHD 125 is enabled and configured to process incoming multimedia signalsto produce audio and visual signals suitable for delivery to display 126and any optional external speakers (not depicted). Incoming multimediasignals received by MHD 125 may be compressed and/or encrypted, digitalor analog, packetized for delivery over packet switched embodiments ofaccess network 130 or modulated for delivery over cable-based accessnetworks. In some embodiments, MHD 125 may be implemented as astand-alone set top box suitable for use in a co-axial or IP-based MCDN.

Referring now to FIG. 3, a block diagram illustrating selected elementsof an embodiment of MHD 125 is presented. In FIG. 3, MHD 125 is shown asa functional component of CPE 122 along with GW 123 and display 126,independent of any physical implementation, as discussed above withrespect to FIG. 2. In particular, it is noted that CPE 122 may be anycombination of GW 123, MHD 125 and display 126.

In the embodiment depicted in FIG. 3, MHD 125 includes processor 301coupled via shared bus 302 to storage media collectively identified asstorage 310. MHD 125, as depicted in FIG. 3, further includes networkadapter 320 that interfaces MHD 125 to LAN 124 and through which MHD 125receives multimedia content 360. GW 123 is shown providing a bridgebetween access network 130 and LAN 124, and receiving multimedia content360 from access network 130.

In embodiments suitable for use in IP based content delivery networks,MHD 125, as depicted in FIG. 3, may include transport unit 330 thatassembles the payloads from a sequence or set of network packets into astream of multimedia content. In coaxial based access networks, contentmay be delivered as a stream that is not packet based and it may not benecessary in these embodiments to include transport unit 330. In aco-axial implementation, however, clients 120 may require tuningresources (not explicitly depicted in FIG. 3) to “filter” desiredcontent from other content that is delivered over the coaxial mediumsimultaneously and these tuners may be provided in MHDs 125. The streamof multimedia content received by transport unit 330 may include audioinformation and video information and transport unit 330 may parse orsegregate the two to generate video stream 332 and audio stream 334 asshown.

Video and audio streams 332 and 334, as output from transport unit 330,may include audio or video information that is compressed, encrypted, orboth. A decoder unit 340 is shown as receiving video and audio streams332 and 334 and generating native format video and audio streams 342 and344. Decoder 340 may employ any of various widely distributed videodecoding algorithms including any of the Motion Pictures Expert Group(MPEG) standards, or Windows Media Video (WMV) standards including WMV9, which has been standardized as Video Codec-1 (VC-1) by the Society ofMotion Picture and Television Engineers. Similarly decoder 340 mayemploy any of various audio decoding algorithms including Dolby®Digital, Digital Theatre System (DTS) Coherent Acoustics, and WindowsMedia Audio (WMA).

The native format video and audio streams 342 and 344 as shown in FIG. 3may be processed by encoders/digital-to-analog converters(encoders/DACs) 350 and 370 respectively to produce analog video andaudio signals 352 and 354 in a format compliant with display 126, whichitself may not be a part of MHD 125. Display 126 may comply with NTSC,PAL or any other suitable television standard.

Storage 310 encompasses persistent and volatile media, fixed andremovable media, and magnetic and semiconductor media. Storage 310 isoperable to store instructions, data, or both. Storage 310 as shown mayinclude sets or sequences of instructions, namely, an operating system312, a remote control application program identified as RC module 314,and EPG 316. Operating system 312 may be a UNIX or UNIX-like operatingsystem, a Windows® family operating system, or another suitableoperating system. In some embodiments, storage 310 is configured tostore and execute instructions provided as services to client 120 byapplication server 150, as mentioned previously.

EPG 316 represents a guide to the multimedia content provided to client120 via MCDN 100, and may be shown to the user as an element of the userinterface. The user interface may include a plurality of menu itemsarranged according to one or more menu layouts, which enable a user tooperate MHD 125. The user may operate the user interface, including EPG316, using RC 128 (see FIG. 2) in conjunction with RC module 314. Insome embodiments, remote viewing application 152, in conjunction withEPG 316, provides functionality for remote viewing of multimedia contenton MCDN terminal devices, as will now be described in further detailbelow.

Local transceiver 308 represents an interface of MHD 125 forcommunicating with external devices, such as RC 128, or another device.Local transceiver 308 may provide a mechanical interface for coupling toan external device, such as a plug, socket, or other proximal adapter.In some cases, local transceiver 308 may be a wireless transceiver,configured to send and receive IR or RF or other signals. Localtransceiver 308 may be accessed by RC module 314 for providing RCfunctionality.

Turning now to FIG. 4, one embodiment of CPE 422, including selectedelements of a detailed embodiment of GW 123, is shown. In FIG. 4, GW 123is shown as a functional component of CPE 422 along with personalcomputer 404, local wireless router 406, MHD 125, displays 126-1 and126-2, and gaming console 416. It is noted that CPE 422 may represent anembodiment of CPE 122 (see FIGS. 2-3). The elements depicted in CPE 422may be arranged independent of any physical implementation, as discussedabove with respect to FIGS. 2-3. In particular, it is noted that CPE 422may be embodied as any physical or mechanical combination of GW 123, MHD125 and display 126, or other elements. It is noted that like numberedelements depicted in FIG. 4 represent identical elements in FIGS. 1-3.

In the embodiment depicted in FIG. 4, GW 123 includes processor 401coupled via shared bus 402 to storage media collectively identified asstorage 410. GW 123, as depicted in FIG. 4, further includes networkadapter 420 that interfaces GW 123 to access network 130 and throughwhich GW 123 receives multimedia content 360. GW 123 is further showncoupled to LAN 424, which provides connectivity to other devicesincluded with CPE 422, as will be discussed in further detail below. GW123 may serve as a bridge between access network 130 and LAN 424, whilereceiving multimedia content 360 from access network 130.

Storage 410 encompasses persistent and volatile media, fixed andremovable media, and magnetic and semiconductor media. Storage 410 isoperable to store instructions, data, or both. Storage 410 as shown mayinclude sets or sequences of instructions, namely, an operating system412, and remote viewing 418. Operating system 412 may be a UNIX orUNIX-like operating system, a Windows® family operating system, oranother suitable operating system. In some embodiments, storage 410 isconfigured to store and execute instructions provided as services toclient 120 by application server 150, as mentioned previously. Remoteviewing 418 may be configured to provide remote viewing to a user of CPE422 and may operate in conjunction with EPG 316 (see FIG. 3).

Local transceiver 408 represents an interface of GW 123 forcommunicating with external devices, such as RC 128, or another device.Local transceiver 408 may provide a mechanical interface for coupling toan external device, such as a plug, socket, or other proximal adapter.In some cases, local transceiver 408 may be a wireless transceiver,configured to send and receive IR or RF or other signals.

LAN 424 may represent a fixed network, a wireless network, or acombination thereof. LAN 424 may represent an exemplary embodiment ofLAN 124 (see FIGS. 2-3). In certain embodiments, local transceiver 408and/or network adapter 420 may provide connectivity for and/or be incommunication with LAN 424. LAN 424 may provide network services forinterconnecting a number of devices, which may be located at a premisesof an MCDN customer. As shown in CPE 422, an exemplary implementation ofLAN 424 provides network connectivity for a number of different types ofMCDN terminal devices, such as personal computer 404, local wirelessrouter 406, MHD 125, and gaming console 416.

Personal computer 404 may represent at least one personal computercoupled to GW 123 for the purpose of obtaining wide-area network accessvia access network 130. In one embodiment, personal computer 404 isprovided network access to the Internet with an MCDN account usingservice provider 121 (see FIG. 1). Local wireless router 406 may serveas a bridge to a wireless network segment at the premises where CPE 422is located, and may include wireless networking components to establishthe wireless network segment. Local wireless router 406 may provideconnectivity to LAN 424 for various types of devices, such as, but notlimited to, wireless communications devices, imaging devices, cameras,portable media players, and personal computers. MHD 125 and TV/display126-1 may represent an embodiment of a television device, such as anIPTV device (see FIGS. 2-3). Gaming console 416 may represent a systemfor playing multimedia games and may be coupled to TV/display 126-2. Incertain embodiments, gaming console 416 may share TV/display 126-1 withMHD 125 (not shown in FIG. 4).

Referring now to FIG. 5, a block diagram illustrating selected elementsof an embodiment of MCDN system 500 is presented. MCDN system 500 isshown with selected elements for providing remote viewing functionality.It is noted that like numbered elements depicted in FIG. 5 representidentical elements in FIGS. 1-4.

In MCDN system 500, switching network 140 and access network 130represent the MCDN client server model, as presented in FIG. 1. Accessnetwork 130 is shown coupled to GW 123, representing equipmentassociated with one of a plurality of MCDN clients (not shown in FIG.5). Mobile content management server 162, shown coupled to switchingnetwork 140, represents one of a number of different MCDN servers thatmay respectively provide various network services to the plurality ofMCDN clients (not shown in FIG. 5).

On the MCDN client side, GW 123 is shown coupled to LAN 424 (see alsoFIG. 4) for providing connectivity to a number of MCDN terminal devices.In MCDN system 500, LAN 424 is directly coupled to the followingrepresentative MCDN terminal devices: MHD with television device 525,gaming console with display 516, and personal computer with display 514.LAN 424 may further be coupled to local wireless router 406, which mayprovide connectivity to portable media player with display 510 via localwireless network 508, representing another MCDN terminal deviceaccessible by GW 123.

In MCDN system 500, GW 123 may further be coupled to another type ofMCDN terminal device, represented by wireless telephone with multimediadisplay 506. GW 123, through access network 130 and switching network140, may communicate with mobile content management server 162 fortransmitting multimedia content and other information. Mobile contentmanagement server 162 may be configured to access mobile network 502,which may be a cellular wide-area network. Mobile network 502 mayinclude wireless network 504, which may be configured to providewireless network service to a plurality of wireless devices, such aswireless telephone with multimedia display 506. Mobile network 502 maybe provided by the same business entity providing MCDN system 500.Alternatively, mobile network 502 may be provided by a differentbusiness entity. Although shown as a singular network in FIG. 5, mobilenetwork 502 may schematically represent a number of different wirelessnetworks and/or wireless network providers coupled to mobile contentmanagement server 162.

In operation, GW 123 may be configured to transmit, or stream,multimedia content to a number of different kinds of MCDN terminaldevices, including MHD with television device 525, gaming console withdisplay 516, personal computer with display 514, portable media playerwith display 510, and wireless telephone with multimedia display 506.Such MCDN terminal devices may be configured to display the multimediacontent. In certain embodiments, a terminal service (not shown in FIG.5) may execute on the MCDN terminal device for receiving and displayingthe multimedia content.

GW 123 may further be configured to respond to a user request via asecond MCDN terminal device to remotely view the displayed multimediacontent of a first MCDN terminal device. Such a request may be issuedvia an RC, such as RC 128 (see FIG. 2). GW 123 may then duplicate themultimedia content from the first MCDN terminal device and display theduplicated multimedia content to the user on the second MCDN terminaldevice. In certain embodiments, the duplicated multimedia content mayinclude multimedia content streamed to the first MCDN terminal device,along with additional user interface elements displayed on the firstMCDN terminal device. The duplicated multimedia content may be displayedon the second MCDN terminal device in the form of high-definition video,standard definition video, or as a picture-in-picture display.

It is noted that GW 123 may transcode the duplicated multimedia contentto a format suitable for the second MCDN terminal device. For example, avideo format for the first MCDN terminal device may not correspond to avideo format for the second MCDN terminal device. It is further notedthat certain DRM issues may restrict the duplication of the multimediacontent displayed on the first MCDN terminal device. In certainembodiments, GW 123 may be configured to obtain DRM authorization forthe duplicated multimedia content. The remote viewing functionalitydescribed above may be implemented in GW 123, for example by remoteviewing 418, in conjunction with remote viewer application 152, usingCPE 422 provided within the scope of services of an MCDN client account.

Turning now to FIG. 6, an embodiment of method 600 for remote viewing ispresented in flow chart form. It is noted that method 600 may beexecuted by remote viewing 418 and/or remote viewer application 152 (seeFIGS. 1, 4). In some embodiments, method 600 may further be executed, atleast in part, by MHD 125 (see FIGS. 2-4). It is further noted thatoperations in method 600 may be rearranged or omitted, as desired.

First multimedia content may be received from an MCDN server (operation602). The first multimedia content may be sent to a first MCDN terminaldevice configured to display the first multimedia content (operation604). DRM authorization to duplicate the first multimedia content may beobtained (operation 606). In certain embodiments DRM authorization maybe obtained from an external source. The first multimedia contentdisplayed on the first MCDN terminal device may be duplicated (operation608). The duplicate multimedia content may be transcoded into a formatsuitable for a second MCDN terminal device (operation 610). Theduplicate multimedia content may be sent to a terminal service executingon the second MCDN terminal device (operation 612). The terminal servicemay receive and cause the duplicate multimedia content to be displayedon the second MCDN terminal device.

Turning now to FIG. 7, an embodiment of method 700 for remote viewing ispresented in flow chart form. It is noted that method 700 may beexecuted by remote viewing 418 and/or remote viewer application 152 (seeFIGS. 1, 4). In some embodiments, method 700 may further be executed, atleast in part, by MHD 125 (see FIGS. 2-4), for example by EPG 318. It isfurther noted that operations in method 700 may be rearranged oromitted, as desired.

A user interface for configuring remote viewing at an MCDN client may bedisplayed (operation 702). User input for selecting a terminal serviceon a first MCDN terminal device or a second MCDN terminal device may bereceived (operation 704). User input for displaying an indication oftranscoding between the first MCDN terminal device and the second MCDNterminal device may be received (operation 706). User input fordisplaying an indication of DRM for duplicate multimedia content may bereceived (operation 708). It is noted that in certain instances, theindication may result in the duplicate multimedia content not beingdisplayed. Previously entered configuration inputs may be saved to astorage or a memory media (operation 710). The previously enteredconfiguration inputs may include the user input received in operations704-708.

Turning now to FIG. 8, user interface 800 illustrating selected elementsof an embodiment of a method for remote viewing is presented. It isnoted that in certain embodiments, user interface 800 may be provided byEPG 318 in conjunction with remote viewer application 152 (see FIGS. 1,4). User interface 800 shows a display of available MCDN terminaldevices at an MCDN client premises for remote viewing. The availabilityof remote viewing is indicated in user interface 800 by the availabilityof Terminal Services on individual MCDN terminal devices. User interface800 further depicts an option to activate individual terminal serviceson the listed MCDN terminal devices by providing the corresponding userinput.

Referring now to FIG. 9, user interface 900 illustrating selectedelements of an embodiment of a method for remote viewing is presented.It is noted that in certain embodiments, user interface 900 may beprovided by EPG 318 in conjunction with remote viewer application 152(see FIGS. 1, 4). User interface 900 may accept user input forconfiguration of terminal services, transcoding, and DRM. User input forselecting the terminal services on the viewing or viewed MCDN terminaldevice may be provided in user interface 900. User input for selectingactivation of an indication for when transcoding is required and/oravailable may be provided in user interface 900. User input forselecting activation of an indication for when DRM is required and/oravailable may be provided in user interface 900. The entered user inputmay be saved to a storage or memory media in user interface 900.

To the maximum extent allowed by law, the scope of the presentdisclosure is to be determined by the broadest permissibleinterpretation of the following claims and their equivalents, and shallnot be restricted or limited to the specific embodiments described inthe foregoing detailed description.

What is claimed is:
 1. A method comprising: receiving, by a systemincluding a processor, a remote viewing request to view media content ona second terminal device of a network client, wherein the media contentwas included in a first multimedia stream that was transmitted, via aservice provider network, to a first terminal device of the networkclient; determining digital rights management rules associated with themedia content that is associated with the remote viewing request; andresponsive to determining that terminal services are resident on adefault device and determining that the digital rights management rulesare satisfied, invoking, by the system, the terminal services of thedefault device to perform terminal service operations fulfilling theremote viewing request including generating a second multimedia streamof the media content by adjusting a format of the first multimediastream and providing the second multimedia stream to the second terminaldevice.
 2. The method of claim 1, wherein the second multimedia streamis based on a transcoding of the first multimedia stream into the formatthat is determined to be suitable for the second terminal device.
 3. Themethod of claim 1, further comprising responsive to determining that theterminal services are not resident on the default device, invoking, bythe system, the terminal services of a non-default device to perform theterminal service operations.
 4. The method of claim 1, furthercomprising generating a first user interface identifying all terminaldevices supporting the terminal services.
 5. The method of claim 1,wherein the step of receiving the remote viewing request comprisesreceiving the remote viewing request from the second terminal device. 6.The method of claim 1, wherein the first terminal device and the secondterminal device are of a device type selected from: a television, apersonal computer, a gaming console, and a mobile multimedia device. 7.The method of claim 6, wherein the device type of the first terminaldevice and the device type of the second terminal device differ.
 8. Themethod of claim 6, wherein the second terminal device comprises a mobilemultimedia device supporting wireless telephony communication.
 9. Anon-transitory computer readable storage medium including processorexecutable program instructions which, when executed by a processorcause the processor to perform operations comprising: receiving a remoteviewing request to view media content on a remote device of a networkclient; accessing remote viewing configuration information indicating adefault device; determining digital rights management rules associatedwith the media content that is associated with the remote viewingrequest; and responsive to determining that terminal services areresident on the default device and determining that the digital rightsmanagement rules are satisfied, invoking the terminal services of thedefault device to perform terminal service operations includinggenerating a second multimedia stream of the media content by adjustinga format of a first multimedia stream of the media content and providingthe second multimedia stream to the remote device.
 10. Thenon-transitory computer readable storage medium of claim 9, wherein thefirst multimedia stream is transmitted, via a service provider network,to a first terminal device of the network client.
 11. The non-transitorycomputer readable storage medium of claim 10, wherein the first terminaldevice is a device selected from: a television, a personal computer, agaming console, and a mobile multimedia device.
 12. The non-transitorycomputer readable storage medium of claim 9, wherein the remote deviceis a mobile multimedia device supporting wireless telephonycommunication.
 13. The non-transitory computer readable storage mediumof claim 9, wherein the second multimedia stream is generated bytranscoding the first multimedia stream into the format that isdetermined to be suitable for the remote device.
 14. The non-transitorycomputer readable storage medium of claim 9, wherein the remote viewingrequest is received from the remote device.
 15. A server, comprising: aprocessor; and a non-transitory computer readable medium, accessible tothe processor, including processor executable program instructionswhich, when executed by the processor cause the processor to performoperations comprising: accessing remote viewing configurationinformation indicating a default device; determining digital rightsmanagement rules associated with media content that is associated with acontent request; and responsive to determining that terminal servicesare resident on the default device and determining that the digitalrights management rules are satisfied, invoking the terminal services ofthe default device to perform terminal service operations includinggenerating a second multimedia stream of the media content by adjustinga format of a first multimedia stream of the media content and providingthe second multimedia stream to a remote device, wherein the firstmultimedia stream is transmitted, via a service provider network, to afirst terminal device of a network client.
 16. The server of claim 15,wherein the second multimedia stream is generated by transcoding thefirst multimedia stream into the format that is determined to besuitable for the remote device.
 17. The server of claim 15, wherein thestep of accessing comprises receiving the remote viewing configurationinformation indicating the default device.
 18. The server of claim 15,wherein the operations further comprise receiving the content requestfrom the remote device.
 19. The server of claim 15, wherein the remotedevice is a device selected from: a television, a personal computer, agaming console, and a mobile multimedia device.
 20. The server of claim15, wherein the first terminal device is a device selected from: atelevision, a personal computer, a gaming console, and a mobilemultimedia device.